🦙 MegaLinter status: ✅ SUCCESS

See detailed report in MegaLinter reports

MegaLinter is graciously provided by

Hi @AxelNennker, thanks for the proposal.

I'd propose to wait until camaraproject/IdentityAndConsentManagement#145 is closed to make this modification, otheruntil that moment the API is not ready to fulfill the Wi-Fi cases requirements.

Additionally, I'd not separate the scenarios in two separated, instead we may need to think in a main (operator token) and fallback scenario (current network-based authcode) that can fulfill both options. Let's discuss it in a audio call, so we can also align other parts of the APi documentation that may require modifications.

I'd propose to wait until camaraproject/IdentityAndConsentManagement#145 is closed to make this modification, otheruntil that moment the API is not ready to fulfill the Wi-Fi cases requirements.

@jgarciahospital yes, the merging should be coordinated with camaraproject/IdentityAndConsentManagement#145. I wanted work on operator token here because NumberVerification is the "natural" use case for operator token.

Additionally, I'd not separate the scenarios in two separated, instead we may need to think in a main (operator token) and fallback scenario (current network-based authcode) that can fulfill both options. Let's discuss it in a audio call, so we can also align other parts of the APi documentation that may require modifications.

It would be nice if you wrote "suggestions" for this PR with the text you prefer. If the discussion here gets lengthy and pros and cons of different ways to do it get hard to resolve, then the meeting is the best place to resolve differences.
That is, of course, just my preferred work mode. You can do it differently.

Regarding declaring operator token the main scenario, I think we are not there yet because the MNO has to have an endpoint that creates the operator token. Usually that endpoint is an Entitlement Server implementing GSMA's TS.43 Service Entitlement Configuration. This is a MNO business decision and a CAMARA business decisison. Here in this group we can enable technology and thereby enable business.

@mengan discusses some variants how the API consumer can get an operator token in #86 (comment) Not all of them are "silent" at least not the first time. It is then for the API consumer to decide whether they want to send the user through that user interaction. The OS vendor might feel the need to ask the user for permission whether the user allows getting an operator token from the carrier for the API consumer at least once.

All, please suggest text or propose topics to consider. Maybe we need a separate CAMARA document (in ICM) discussing e.g. operator token use cases. Or such a use case could be added to https://github.com/camaraproject/NumberVerification/blob/main/documentation/API_documentation/NumberVerification_verify_User_Story.md or both...
I do not cling to my text proposal made in this PR.